-
Notifications
You must be signed in to change notification settings - Fork 92
[SREP-1045] Develop Clusterrole webhook #379
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
} | ||
|
||
// Protected ClusterRoles that should not be deleted | ||
protectedClusterRoles = []string{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this a full list? it mentioned backplane-* in the description.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The full list will contain any backplane related clusterroles + most openshift critical. Its not fiesible to include all system:*
roles as they can change over time, and we still want customers being able to create and remove their own clusterroles. The idea is being able to get access to the cluster if some clusterroles have been deleted.
@diakovnec: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
/label tide/merge-method-squash |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bmeng, diakovnec The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This PR is for implementing a new clusterrole webhook. We have a way to test it for Rosa Classic, but it is complicated for HCP because of image embedding and ACM policies that deploy the package to the HCP namespace.
One of the possible ways is to merge PR into the stage and verify if it provisions all resources as expected.
The functionality of the webhook itself has been verified for Rosa Classic and theoretically should work for HCP as long as it's enabled with
func (s *ClusterRoleWebHook) HypershiftEnabled() bool { return true }
Also, the purpose of this PR is to check the e-2-e pipeline process.
Note: more context in the Slack Discussion
Test for Classic Rosa